Is this a new bug in XR5? It doesn't seem to show up on a couple of machines here that run a vendor's XR4 (mips RISCwindows in particular). Since they had to modify the R4 xterm code to deal with their own brand of pty stuff, perhaps they fixed it either inadvertently or otherwise. I don't have R4 source lying around any more to check. Basically, if I try to set the log file to an unreadable file either through -lf, the X resource or a link, logging won't turn on at all. Just curious, Dave Goldberg Post: The Mitre Corporation MS B020 202 Burlington Rd. Bedford, MA 01730 Phone: 617-271-3887 Domain: dsg@mitre.org UUCP: {your neighborhood}!linus!mdf!dsg